Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1819

reference: 733-tree-1
name: 1819
tree-preservation-order: undefined
733-tpo-1
uprn
address-text
point: POINT (-0.978512 50.866339)
geometry: MULTIPOLYGON (((-0.978314 50.866318,-0.978322 50.866357,-0.978350 50.866392,-0.978393 50.866420,-0.978448 50.866439,-0.978510 50.866445,-0.978571 50.866440,-0.978627 50.866422,-0.978672 50.866395,-0.978701 50.866360,-0.978711 50.866321,-0.978702 50.866282,-0.978675 50.866247,-0.978632 50.866219,-0.978576 50.866200,-0.978515 50.866194,-0.978454 50.866199,-0.978398 50.866217,-0.978353 50.866244,-0.978324 50.866279,-0.978314 50.866318)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL